I've been testing this and I had to run docker compose up -d a few times for the site to come up. The drupal container fails running docker compose up the first time. Then I run it again and drupal starts as well as solr. I think that issue is that solr is not starting the first time around and that is what is making the drupal container fail. Update: the docker compose file says solr depends on a healthy drupal container so maybe the failure is caused by something else. Currently I can't log in to drupal as admin (using password.) So I tried several of the passwords in the secrets folder (including the drupal default account password) and nothing will work. I will try to debug more tomorrow.

Great!

Documenting yq as a requirements is probably the only blocker.

As mentioned above, since the init scripts that call generate secrets/certs runs in a new init service, the only host dependencies are docker and make. Make is technically optionally if you don't want to utilize those helper utilities

Just tested this again and I'm getting an error with the drupal container:
✘ Container isle-site-template-drupal-1 Error dependency drupal failed to start 0.5s dependency failed to start: container isle-site-template-drupal-1 is unhealthy make: *** [Makefile:42: up] Error 1
I tried to run docker compose down then dock compose up -d but the same error occurs.

Docker ps shows that there is no solr container which makes sense since drupal is marked unhealthy.

I ran make status:
`--- General Status ---
Site mode: Development
COMPOSE_PROJECT_NAME: isle-site-template
ISLANDORA_TAG: 6.2.7
--- Configuration Warnings ---
Mount drupal codebase into drupal container for local development
For easier local development, you can link the sample docker-compose override file.
This allows you to mount your local Drupal codebase into the container.
To do so you can run the following command:
ln -s docker-compose.sample.yml docker-compose.override.yml
And then run make up for the changes to apply.

Update COMPOSE_PROJECT_NAME in .env
Docker Compose uses this name to prefix containers, networks, and volumes.
Running multiple projects with the same name on one machine will cause conflicts.
This is mostly relevant for development environments that may have multiple ISLE sites
But may also be a concern is a single host serves multiple ISLE sites.
Ensure this value is unique if you run other Docker Compose projects.

JWT key pair: Valid: secrets/JWT_PUBLIC_KEY and secrets/JWT_PRIVATE_KEY match

--- Traefik Status ---

HTTP port: 80
HTTPS port: 443
DOMAIN: islandora.traefik.me
URL: http://islandora.traefik.me
TLS_PROVIDER: self-managed
Traefik container is not running.
Domain islandora.traefik.me resolves to: 127.0.0.1`

So I ran this:
ln -s docker-compose.sample.yml docker-compose.override.yml
Then make up again and it brought the site up.

I will test this again making the override file first then running make up.

I made a fresh isle-site-template and ran this:
ln -s docker-compose.sample.yml docker-compose.override.yml
Then make up and the drupal container was unhealthy. I shelled into the container and the permissions for all the files in the drupal folder were 100:nginx. I changed them to nginx:nginx and ran make up again and it worked.

@aOelschlager - are you on the latest version of this PR? docker-compose.sample.yml no longer exists. I think maybe some of the changes made in this PR since you last tested may be causing the failures. This should clear them up:

git reset --hard
git pull origin rm-profiles
make clean
make up

ah i neglected to update the helper text 364f760

I noticed that I should be using the dev as the override file shortly after my last comment. I tested it again and the drupal container was unhealthy. I shelled into the contain and the permissions were mixed. Some had nginx:nginx and some had 100:nginx. I'll test it again and see if that is reproducible.